Same here. God damn it. All this technology and geniuses and they still can't deal with the most basic thing of all: RE-ACTIVATE accounts immediately after purchase

Dude just Google it. Ai will tell u step by step.

Everybody.. lets DEMAND: ‼️NO MORE ANUAL FEES for Developer program ‼️ They are letting all these AI 🗑️ apps and flooding it. Each update waiting 2 weeks min.💩

Yes, it's getting really annoying, 2 weeks min for each update. This is obviously caused by Apple allowing Vibe Apps. Lot of trash AI 🗑️coming in. I wouldn't mind but they need to get rid of the anual fee for the Developer program then.

Cause they open the AI floods of hell. You can soon expect a month of waiting time while they keep collecting the anual fee 🤑

This was expected. Apple open the AI flood gates with those agent in XCode. Meaning repeating trash Apps are overpopulating the Store and in consequence, unjustified weeks long review times. This is a big🖕 to the Developer community, 🍏is siding with AI generators, which now PIRATE our code directly through agents. They should at least have the decency to remove the anual fee, but no.. too much greed involved🤑

I can confirm there is something crashing my Apps that only have Launchscreen storyboards. I use Autoresizing and not Autolayout. And guys please, make a real effort to build a Launchscreen component in SwiftUI. It makes no sense in 2026, always ten years after and we still have a storyboard file messing/crashing our Apps in Swift.

Sup, My advise is not to compare yourself nor try to copy other success stories. Specially, do not shape you Apps to cater to other people's wishes. Make something that you enjoy and that you would definitely buy or try. Let the creativity flow. Also, exploit the advantage of AI that Devs have these days: Which is having the Wizard of Oz write code for you by simple asking Google ✨

Hello again, So, they are two issues. The crash and the iCloud sync dealing with this new @Attribute "trasformables" that Apple change for us and thus, provoking this mess. In all honestly, Apple is the one that should be making the Tweaks, not us. In-memory models should respect the existing data store of our Apps since they are already being used by thousands of users in realtime. Someone above probably doesn't want to deal with the iOS26.2 publishing date (it's in the final stages) and that is the wrong decision. Why do we have to clean the mess when Apple made our code incompatible? 😒. Makes no sense. ** ** Are you aware how many weeks of work it will take for us to refactor all of our Apps using this confusing tweak with decodables? Sorry but your solution is not acceptable.

Just a quick update: This fix helps avoid the crash but it does not solve the issue cause by iOS26.1, which automatically changes SwiftData Arrays or Sets attributes from .externalStorage to .transformable. This in consequence blocks the iCloud sync mirroring and results with the full disappearance Customer's data after updating. It is a serious bug that needs to be address by Apple ASAP.

This is serious stuff. Apple should add a fix to this with iOS26.2 I found a way to avoid the crash but due to this change from @Attribute(.externalStorage) to @Attribute(.transformable), which we never made ourselves.. it's blocking complete iCloud sync mirroring of existing records. Meaning, Customers don't see their data anymore. As Developers, there is really little we can do. This an issue that Apple needs to fix as soon as possible. Thank you

Hi Chen, I don't believe it has anything to do with "Transformables", in my opinion that is some another warning for handling image formats or colors but the image gets through just fine. I've had that warning way long before. I honestly think Apple should hold on the iOS26.2 before they fix this. It's messing millions of SwiftData Apps already published (customers are already pissed). Look at this answer I posted a few hours ago, it might help: https://developer.apple.com/forums/thread/808020

Try this: switch result { case .success(let verification): //Check whether the transaction is verified. If it isn't, //this function rethrows the verification error. let transaction = try checkVerified(verification) //The transaction is verified. Deliver content to the user. await updateCustomerProductStatus() //Always finish a transaction. await transaction.finish() return transaction case .userCancelled, .pending: return nil default: return nil }

Hello, Thanks for the assistance. I think I found the issue. It has to do with they way we construct the ModelContainer inside the init method. The Answer is in the photos attached. With this change, the App preserves the data and opens just fine in iOS26.1 I just need update all my Apps before sales go down 😅

Punish them, not me. Many customers unlock features just cause they know they’ll receive a refund. Stop doing that Apple.. cause as you can see, they will abuse the system. Any purchase after 5 min. should be INELIGIBLE for refund. Stop pampering customers and protect Devs. Skipping my monthly income is completely unacceptable! Worst of all.. no response from them whatsoever. They just decided not to pay me for my sales and stay silent.